Skip to content

Add nullboot.conf support with a kernel-priority field - #166

Open
julian-klode wants to merge 2 commits into
mainfrom
flavour-order
Open

Add nullboot.conf support with a kernel-priority field#166
julian-klode wants to merge 2 commits into
mainfrom
flavour-order

Conversation

@julian-klode

Copy link
Copy Markdown
Contributor

Field is using the same spelling as the grub one.

This allows preferring certain kernel flavours over others.

Not sure if the drop-ins appending flavour order is sensible, probably they should just override instead as it is a bit confusing coming from other configurations.

@julian-klode

Copy link
Copy Markdown
Contributor Author

Maybe we need to have

flavour-order:

and

flavour-order-append:

@julian-klode julian-klode changed the title Add nullboot.conf support with a flavour-order field Add nullboot.conf support with a kernel-priority field Sep 9, 2026
Implement nullboot.conf and nullboot.conf.d - yaml files. At this
point parse only kernel-priority (similar to GRUB_FLAVOUR_ORDER in
grub).

Assisted-by: LLM
Wrap version.Version in a WeightedVersion that carries a priority
computed from the kernel-priority configuration. Kernels with higher
priority sort first; equal priorities fall back to version order.

Assisted-by: LLM
@julian-klode

Copy link
Copy Markdown
Contributor Author

We now have

kernel-priority:
    fips: 1000
    azure-fde: 100

with unspecified suffixes defaulting to 0. I think this is a bit more cleaner, and the dict merges naturally.

This is overkill, a single preference would also get the job done preferred-kernel:, but it's arguably a bit cleaner if you ever end up entering the firmware boot menu to manually select an entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant